Conversation
release notes Signed-off-by: Claire Rye <claire.rye@auckland.ac.nz>
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces the release notes for the AGDR platform's March 18, 2026 update. It primarily documents the integration of the REMS system for managing data access and submission applications, alongside a comprehensive list of updated versions for various core components and internal microservices, ensuring transparency and clarity regarding the current state of the platform. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces the release notes for March 18, 2026. The content appears correct for a release note. I've added a few suggestions to improve the markdown formatting for consistency and readability by removing superfluous blank lines and whitespace.
| - AGDR Internal helm chart: 1.3 | ||
| - REMS: 1.0 | ||
|
|
||
|
|
There was a problem hiding this comment.
There is an extra blank line here between the main versions list and the micro-services list. Using a single blank line for separation is more conventional and improves source readability. Please consider removing this superfluous line.
|
|
||
| Note: *JupyterHub* is excluded as not used in AGDR. | ||
|
|
||
|
|
There was a problem hiding this comment.
Similar to a previous comment, there is an extra blank line here. For consistency and cleaner source code, it's recommended to use only a single blank line to separate sections.
|
|
||
|
|
||
| ## New and Improved | ||
|
|
There was a problem hiding this comment.
This line consists only of whitespace characters. While many Markdown parsers treat this as a blank line, it's best practice to use a truly empty line for this purpose. This avoids ambiguity and potential issues with tools that trim trailing whitespace.
1 participant
release notes